Elaborate on our policy for supporting JVM versions #1042
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There are two axes regarding the required or supported JVM version: - running Scala code, - compiling Scala code, and on both there is a lower and upper bound of the supported JVM.
retronym
reviewed
Mar 23, 2018
| ### Running versus compiling and required / supported JVM | ||
| For most users, we recommend using Java 8 for *compiling* (and running) Scala code. Since the JVM is backward compatible, it is usually safe to use a newer JVM to *run* your code compiled by the Scala compiler for older JVM versions. There are notable exceptions with experimental/unsafe features, and the introduction of the module system in Java 9. The Scala compiler does usually need updates to run properly on newer versions of the JVM, so make sure to use the appropriate JVM when compiling your code. | ||
|
|
||
| Issues with using the Scala compiler on *non-LTS* versions of Java will not necessarily be considered blockers for releases, but we will do our best to run CI on more versions of Java to catch bugs early, and to fix them as quickly as reasonably possible. If regressions do occur with non-LTS (or, generally, unsupported) versions of Java, we may bring the next minor release deadline a bit closer, so that these issues are generally resolved within a month or two. Lightbend does offer commercial support for faster resolution of issues like this. |
retronym
reviewed
Mar 23, 2018
| | 6 | 2.11.0, 2.10.0 | | ||
|
|
||
| ### Running versus compiling and required / supported JVM | ||
| For most users, we recommend using Java 8 for *compiling* (and running) Scala code. Since the JVM is backward compatible, it is usually safe to use a newer JVM to *run* your code compiled by the Scala compiler for older JVM versions. There are notable exceptions with experimental/unsafe features, and the introduction of the module system in Java 9. The Scala compiler does usually need updates to run properly on newer versions of the JVM, so make sure to use the appropriate JVM when compiling your code. |
Member
There was a problem hiding this comment.
This limits the user from being able to call Java 9 APIs. Perhaps we should be explicit about that restriction.
Member
|
There are probably more steps in our support.
These might require a blog to articulate and relate to our roadmap, so the approximation you've started with could be enough for this document. |
SethTisue
approved these changes
Mar 23, 2018
Member
|
Jason has made some suggestions that aren't addressed, but I suggest we merge anyway since this is topical right now because of the regression in 2.12.5. We can always improve it more later. |
dwijnand
reviewed
Mar 23, 2018
| This table shows the first Scala release in each series that works with each JVM release. | ||
|
|
||
| | JVM version | First Scala compiler release supported to run on this JVM | | ||
| | JVM version | Minimum Scala versions | |
Member
There was a problem hiding this comment.
to me specifying "compiler" here was helpful..
Member
|
I'll loop back to update this to complement my forthcoming blog on the topic. |
jvican
reviewed
Mar 30, 2018
| ## JDK 9 compatibility notes | ||
| ## Running versus compiling | ||
|
|
||
| For most users, we still recommend using Java 8 for *compiling* (and running) Scala code. Since the JVM is backward compatible, it is usually safe to use a newer JVM to *run* your code compiled by the Scala compiler for older JVM versions. There are notable exceptions with experimental/unsafe features, and the introduction of the module system in Java 9. The Scala compiler does usually need updates to run properly on newer versions of the JVM, so make sure to use the appropriate JVM when compiling your code. |
Member
There was a problem hiding this comment.
I suggest removing the parenthesis in (and running).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are two axes regarding the required or supported JVM version:
and on both there is a lower and upper bound of the supported JVM.